home *** CD-ROM | disk | FTP | other *** search
- Path: comma.rhein.de!serpens!not-for-mail
- From: mlelstv@serpens.rhein.de (Michael van Elst)
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: OS features
- Date: 31 Jan 1996 22:03:20 +0100
- Organization: dis-
- Message-ID: <4eoleo$fjd@serpens.rhein.de>
- References: <4e657d$2db@news.rhrz.uni-bonn.de> <4950.6603T1192T1630@teclink.net> <4eoeid$k6f@news.rhrz.uni-bonn.de>
- NNTP-Posting-Host: serpens.rhein.de
-
- fasten@zeus.informatik.uni-bonn.de (Bernhard Fastenrath) writes:
-
- >A unix system call switches to kernel mode and back to user mode by means of
- >an interrupt without a context switch, this sounds more like what I had in mind.
- >It should be possible to make a low-overhead switch to another mode when a
- >system library that requires special permissions is called.
-
- A UNIX system call is _slow_ compared to Exec task switching. That's why
- every efficient system tries to move as much data as possible with a single
- system call.
-
- With X11 it is even worse since every command has to be funneled through the
- network system (even when it is local, a real network of course is slower).
- The X11 protocol therefore even queues many commands and operation is asynchronous
- (i.e.: without results) if possible. The X11 library does a great deal of caching
- results to avoid communication latency.
-
- You see that a protected system requires different algorithms than an unprotected
- system.
-
- >: Are you willing to sacrifice the speed to do these checks on almost every
- >: intiution function call?
-
- >Make it optional (sys:prefs/kernel).
-
- Sorry. This doesn't help. Then you could make the whole protection a debugging tool and
- avoid the work of rewriting the system.
-
- --
- Michael van Elst
-
- Internet: mlelstv@serpens.rhein.de
- "A potential Snark may lurk in every tree."
-